Access point (AP) controlled uplink RTS/CTS configuration and disablement

ABSTRACT

The present disclosure provides techniques for configuring the utilization of request-to-send/clear-to-send (RTS/CTS) protocol procedures based on varying conditions at the STA. For example, an AP may identify one or more conditions, when satisfied, may trigger the STA to either enable or disable uplink (UL) transmissions associated with a RTS/CTS protocol procedure. In some aspects, an AP may determine a transmit opportunity (TXOP) threshold for an STA and may determine whether to broadcast a message having the TXOP threshold to multiple STAs including the STA or unicast the message to the STA. An STA may receive a message from an AP having a TXOP threshold and may replace, based on an indication in the received message, a current TXOP threshold in the STA with the TXOP threshold in the received message. The STA may transmit an UL RTS frame in response to a determination that a planned TXOP duration satisfies the TXOP threshold.

CLAIM OF PRIORITY UNDER 35 U.S.C. § 120

The present application claims priority to Provisional Application No.62/291,430 entitled “ACCESS POINT (AP) CONTROLLED UPLINK RTS/CTSCONFIGURATION AND DISABLEMENT,” and filed Feb. 4, 2016, and furtherclaims priority to Provisional Application No. 62/209,680 of same title,and filed Aug. 25, 2015. Both the Provisional Applications are assignedto the assignee hereof and hereby expressly incorporated by referenceherein.

BACKGROUND

The present disclosure relates generally to communication systems, andmore particularly, to techniques for access point (AP) controlled uplinkrequest-to-send/clear-to-send (RTS/CTS) configuration and disablement ina wireless network.

The deployment of wireless local area networks (WLANs) in the home, theoffice, and various public facilities is commonplace today. Suchnetworks typically employ a wireless access point (AP) that connects anumber of wireless stations (STAs) in a specific locality (e.g., home,office, public facility, etc.) to another network, such as the Internetor the like. A set of STAs can communicate with each other through acommon AP in what is referred to as a basic service set (BSS). However,some WLAN network deployments may be dense (e.g., have a large number ofSTAs deployed within the coverage area of multiple APs), which mayresult in issues related to channel or medium usage. In other examples,the wireless network may be configured as an “ad-hoc” communicationsystem in which terminals asynchronously communication directly witheach other without use of any specific AP.

Thus, with multiple STAs and APs operating in a limited area, trafficcollisions and interferences may occur among STAs and/or APs attemptingto access the wireless medium. In some aspects, various techniques andsystems have been developed to avoid or minimize traffic collisions(e.g., where multiple STAs attempt to access the wireless mediumsimultaneously) by coordinating access to the wireless medium. Oneexample of collision avoidance (CA) system may be a utilization ofRTS/CTS protocol procedure. RTS/CTS protocol procedure are an optionalmechanism used by the Institute of Electrical and Electronics Engineers(IEEE) 802.11 wireless networking protocol to reduce, for example, framecollisions introduced by the hidden node problem (e.g., when a node isvisible from an AP, but not from other nodes communicating with the AP).

However, conventional system's reliance on a rigid RTS/CTS protocolprocedure regardless of varying conditions in the wireless network mayraise other issues that adversely affect overall network performance. Inone example, utilization of conventional RTS/CTS protocol may result inthe exposed terminal problem where a wireless node (e.g., overlappingbasic service set (OBSS) node) that is nearby, but associated withanother AP may overhear the exchange, and thus be forced to backoff andcease transmitting for the specified period in the RTS. In otherexample, transmitting RTS/CTS frame or packets prior to accessing thewireless medium may be counter intuitive where the uplink framescheduled for transmission has a shorter duration than the RTS/CTSprotocol procedure itself.

SUMMARY

The present disclosure provides various aspects related to techniquesfor configuring the utilization of RTS/CTS protocol procedures based onvarying conditions at the STA. For example, in some aspects, an AP mayidentify one or more conditions, when satisfied, may trigger the STA toeither enable or disable uplink (UL) transmissions associated with aRTS/CTS protocol procedure. Additionally or alternatively, in someaspects, an AP may determine a transmit opportunity (TXOP) threshold foran STA and may determine whether to broadcast a message having the TXOPthreshold to multiple STAs including the STA or unicast the message tothe STA. The AP may then broadcast or unicast the message in accordanceto the determination. Additionally or alternatively, in some aspects, anSTA may receive a message from an AP having a TXOP threshold and mayreplace, based on an indication in the received message, a current TXOPthreshold in the STA with the TXOP threshold in the received message.The STA may transmit an UL RTS frame in response to a determination thata planned TXOP duration satisfies the TXOP threshold.

In one example, a method for wireless communication is disclosed. Themethod may include identifying, at an AP, one or more frame types for ULtransmissions associated with a RTS/CTS protocol. The one or more frametypes being identified from a plurality of frame types supported by aSTA for the UL transmission. In some examples the method may furtherinclude transmitting a configuration message to the STA. Theconfiguration message may include configuration information indicatingthe one or more frame types, one or more conditions for the STA to usethe one or more frame types, and one or more transmission parametervalues for the STA to transmit with the one or more frame types.

In some examples, the method may include another method for wirelesscommunication. The method may include receiving, at the STA, aconfiguration message from an AP. The configuration message may includeconfiguration information indicating one or more frame types for ULtransmissions associated with a RTS/CTS protocol, one or more conditionsfor the STA to use the one or more frame types, and one or moretransmission parameter values for the STA to transmit with the one ormore frame types. In some examples, the method may include configuringthe STA based on the configuration information provided in theconfiguration message.

In another example, an apparatus for wireless communication isdisclosed. The apparatus may include a processor and a memory coupled tothe processor. The memory may include instructions executable by theprocessor to identify, at an AP, one or more frame types for ULtransmissions associated with a RTS/CTS protocol. The one or more frametypes being identified from a plurality of frame types supported by aSTA for the UL transmission. In some examples the instructions may befurther executable by the processor to transmit a configuration messageto the STA. In some examples, the configuration message may includeconfiguration information indicating the one or more frame types, one ormore conditions for the STA to use the one or more frame types, and oneor more transmission parameter values for the STA to transmit with theone or more frame types.

In yet further example, another apparatus for wireless communication isdisclosed. The apparatus may also include a processor and a memorycoupled to the processor. The memory may include instructions executableby the processor to receive, at the STA, a configuration message from anAP. The configuration message may include configuration informationindicating one or more frame types for UL transmissions associated witha RTS/CTS protocol, one or more conditions for the STA to use the one ormore frame types, and one or more transmission parameter values for theSTA to transmit with the one or more frame types. In some examples, theinstructions may further be executable by the processor to configure theSTA based on the configuration information provided in the configurationmessage.

It is understood that other aspects of apparatuses and methods willbecome readily apparent to those skilled in the art from the followingdetailed description, wherein various aspects of apparatuses and methodsare shown and described by way of illustration. As will be realized,these aspects may be implemented in other and different forms and itsseveral details are capable of modification in various other respects.Accordingly, the drawings and detailed description are to be regarded asillustrative in nature and not as restrictive

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B shows an example wireless communication system in whichaspects of the present disclosure may be employed.

FIGS. 2A and 2B are flowcharts of example methods of wirelesscommunication implemented on an AP in accordance with various aspects ofthe present disclosure.

FIGS. 3A and 3B are flowcharts of example methods of wirelesscommunication implemented on an STA in accordance with various aspectsof the present disclosure.

FIG. 4 shows hardware implementation of an AP that may be employedwithin a wireless communication system in accordance with variousaspects of present disclosure.

FIG. 5 shows hardware implementation of an STA that may be employedwithin a wireless communication system in accordance with variousaspects of present disclosure.

FIG. 6 shows a chart illustrating an example RTS/CTS overhead as afunction of TXOP.

FIG. 7 shows a block diagram illustrating a control information element(IE) in accordance with various aspects of present disclosure.

FIG. 8A is a flowchart of another example method of wirelesscommunication implemented on an AP in accordance with various aspects ofthe present disclosure.

FIG. 8B is a flowchart of another example method of wirelesscommunication implemented on an STA in accordance with various aspectsof the present disclosure.

FIG. 9A is a flowchart of an example method of wireless communicationimplemented on an AP in accordance with various aspects of the presentdisclosure.

FIG. 9B is a flowchart of an example method of wireless communicationimplemented on a STA in accordance with various aspects of the presentdisclosure.

DETAILED DESCRIPTION

Various concepts will be described more fully hereinafter with referenceto the accompanying drawings. These concepts may, however, be embodiedin many different forms by those skilled in the art and should not beconstrued as limited to any specific structure or function presentedherein. Rather, these concepts are provided so that this disclosure willbe thorough and complete, and will fully convey the scope of theseconcepts to those skilled in the art. The detailed description mayinclude specific details. However, it will be apparent to those skilledin the art that these concepts may be practiced without these specificdetails.

As discussed above, wireless network technologies may include varioustypes of WLANs. A WLAN may be used to interconnect nearby devicestogether, employing widely used networking protocols. Some WLAN networkdeployments may be dense (e.g., have a large number of STAs deployedwithin the coverage area of multiple APs), which may result in issuesrelated to channel or medium usage. The various aspects described hereinmay apply to any communication standard, such as WiFi or, moregenerally, any member of the IEEE 802.11 family of wireless protocols.

In some aspects, wireless nodes or devices, such as stations and APs,may interact in a Carrier Sense Multiple Access (CSMA) type network,such as a network that conforms to the 802.11ah standard. CSMA is aprobabilistic Media Access Control (MAC) protocol. “Carrier Sense”describes the fact that a wireless device attempting to transmit on achannel may use feedback from its receiver to detect a carrier wavebefore trying to send its own transmission. “Multiple Access” describesthe fact that multiple wireless devices may send and receive on a sharedchannel. Accordingly, in a CSMA type network, a transmitting wirelessdevice senses the channel and if the channel is busy (i.e. anotherwireless device is transmitting on the channel), the transmittingwireless device will defer its transmission to a later time. If,however, the channel is sensed as free, then the transmitting wirelessdevice may transmit its data on the channel.

Clear Channel Assessment (CCA) is used to determine the state of thechannel before a wireless device attempts to transmit thereon. The CCAprocedure is executed while a wireless device's receiver is turned onand the wireless device is not currently transmitting a data unit suchas a packet. A wireless device may sense whether the channel is clearby, for example, detecting the start of a packet by detecting thepacket's PHY preamble. This method may detect relatively weaker signals.Accordingly, there is a low detection threshold with this method. Analternative method is to detect some energy on the air, which may bereferred to as energy detection (ED). This method is relatively moredifficult than detecting the start of a packet and may only detectrelatively stronger signals. As such, there is higher detectionthreshold with this method. In general, detection of anothertransmission on the channel is a function of the received power of thetransmission, where the received power is the transmitted power minusthe path loss.

Other CSMA transmission architectures may be employed as disclosedherein. RTS/CTS is one such protocol discussed below that relies onconditions established by the station (STA). RTS/CTS is an optionalmechanism or protocol used in a CSMA environment, such as 802.11ah, toreduce data collisions. Often data collisions are the result of a“hidden” wireless device, referred to as a “hidden node.” A hidden nodeor wireless device in this context refers to a wireless device that isout of range of the transmitting wireless device, but in range of thereceiver. The “request” and “clear” messages alleviate much of thehidden node problem.

In particular, in a CSMA environment, RTS/CTS functions as a method forvirtual carrier sensing as is implemented in CSMA/CA (Carrier SenseMultiple Access with Collision Avoidance). A wireless device thatintends to send data (transmitter device) initiates an RTS frame to one(unicast) or more (multicast, broadcast) wireless devices indicating theintent to transmit data. The receiving or receiver device (or devices)replies with a CTS frame, indicating that it is ready to receive thetransmission. In some instances, the RTS frame is sent as part of anuplink (UL) transmission with a respective CTS frame response providedin a downlink (DL) transmission. In other instances, the CTS frame issent as part of an UL transmission in response to a respective RTS frameprovided in a DL transmission. The RTS/CTS frames also includeinformation regarding a time period in which any other wireless devicesreceiving the frames should not attempt to access the medium.

In some aspects of the present disclosure, RTS/CTS may be implementedunder circumstances dictated by a predetermined threshold. An exemplarypredetermined threshold may indicate a minimum packet size before theRTS/CTS protocol is implemented. In certain circumstances, the STA mayimplement the RTS/CTS protocol when packets exceed such a threshold, anddisable the RTS/CTS protocol when the packet size is less than thethreshold. In accordance with aspects of the present disclosure, greaterefficiencies may be realized and data collisions reduced in anarchitecture allowing a more flexible implementation of RTS/CTS. Forinstance, thresholds or rules for RTS/CTS implementation that areadaptive or set based on one or more conditions (e.g., wireless linkconditions or conditions realized by the STA or the AP) may providegreater transmission efficiency and reduce data collisions.

Accordingly, in some aspects of the present disclosure, an AP mayconfigure one or more STAs by identifying one or more frame types of ULtransmissions associated with a RTS/CTS protocol and the one or moreconditions for the STA to use the one or more frame types. The one ormore frame types may include, but are not limited to, legacy RTS/CTS(e.g., frame type as control and subtype as RTS/CTS), legacy RTS/CTS incontrol wrapper frame type where the control wrapper contains contentsof legacy RTS/CTS in addition to a high-throughput (HT) control field asdescribed in current standard or any future modifications to the currentstandard, modified legacy RTS/CTS where contents of legacy RTS/CTS areredefined to carry new information (e.g., one or more bits in a MACaddress field of a legacy CTS may be redefined to carry a BSS identifierto help nodes drop OBSS frames for better medium reuse, etc.),directional multi-gigabit (DMG) CTS, DMG CTS in control wrapper frametype, modified DMG CTS, RTS/CTS with new control frame subtype, andRTS/CTS for multi-user operations. Additionally or alternatively, eachRTS/CTS frame type may offer a different deferral rule. For example,legacy RTS/CTS may be deferred at any time, while RTS/CTS in new controlframe subtype with BSS identifier may be dropped by an OBSS node. As aresult, in accordance with aspects of the present disclosure, an AP mayconfigure one or more STAs in the wireless network to utilize differentUL RTS/CTS frame types based on one or more conditions observed at theSTA and/or the AP (e.g., if the STA is at the cell edge, the AP mayconfigure the STA to utilize legacy RTS/CTS). In some aspects, AP mayconfigure the STAs to include additional information in the UL RTS/CTSmessages in order to achieve improved performance (e.g., medium reuse,link adaptation, scheduling, etc.).

FIG. 1A is a conceptual diagram 102 illustrating an example of awireless local area network (WLAN) deployment in connection with varioustechniques described herein. The WLAN may include one or more accesspoints (APs) and one or more mobile stations (STAs) associated with arespective AP. In this example, there are two APs deployed: AP1 105-a inbasic service set 1 (BSS1) and AP2 105-b in BSS2, which may be referredto as an OBSS. AP1 105-a is shown as having at least three associatedSTAs (STA1 115-a, STA2 115-b, and STA3 115-c) and coverage area 110-a,while AP2 105-b is shown having one associated STA4 115-d) and coveragearea 110-b. The STAs 115 and AP 105 associated with a particular BSS maybe referred to as members of that BSS. In the example of FIG. 1, thecoverage area of AP1 105-a may overlap part of the coverage area of AP2105-b such that STA1 115-a may be within the overlapping portion of thecoverage areas. The number of BSSs, APs, and STAs, and the coverageareas of the APs described in connection with the WLAN deployment ofFIG. 1 are provided by way of illustration and not of limitation.

In some examples, the APs (e.g., AP1 105-a and AP2 105-b) shown in FIG.1 are generally fixed terminals that provide backhaul services to STAs115 within its coverage area or region. In some applications, however,the AP may be a mobile or non-fixed terminal. The STAs (e.g., STA1115-a, STA2 115-b, STA3 115-c, STA4 115-d) shown in FIG. 1, which may befixed, non-fixed, or mobile terminals, utilize the backhaul services oftheir respective AP to connect to a network, such as the Internet.Examples of an STA include, but are not limited to: a cellular phone, asmart phone, a laptop computer, a desktop computer, a personal digitalassistant (PDA), a personal communication system (PCS) device, apersonal information manager (PIM), personal navigation device (PND), aglobal positioning system, a multimedia device, a video device, an audiodevice, a device for the Internet-of-Things (IoT), or any other suitablewireless apparatus requiring the backhaul services of an AP. An STA mayalso be referred to by those skilled in the art as: a subscriberstation, a mobile unit, a subscriber unit, a wireless unit, a remoteunit, a mobile device, a wireless device, a wireless communicationsdevice, a remote device, a mobile subscriber station, an accessterminal, a mobile terminal, a wireless station, a remote terminal, ahandset, a user agent, a mobile client, a client, user equipment (UE),or some other suitable terminology. An AP may also be referred to as: abase station, a base transceiver station, a radio base station, a radiotransceiver, a transceiver function, or any other suitable terminology.The various concepts described throughout this disclosure are intendedto apply to all suitable wireless apparatus regardless of their specificnomenclature.

Each of STA1 115-a, STA2 115-b, STA3 115-c, and STA4 115-d may beimplemented with a protocol stack. The protocol stack can include aphysical layer for transmitting and receiving data in accordance withthe physical and electrical specifications of the wireless channel, adata link layer for managing access to the wireless channel, a networklayer for managing source to destination data transfer, a transportlayer for managing transparent transfer of data between end users, andany other layers necessary or desirable for establishing or supporting aconnection to a network.

Each of AP1 105-a and AP2 105-b can include software applications and/orcircuitry to enable associated STAs to connect to a network viacommunications link 125. The APs can send frames or packets to theirrespective STAs and receive frames or packets from their respective STAsto communicate data and/or control information (e.g., signaling).

Each of AP1 105-a and AP2 105-b can establish a communications link 125with an STA that is within the coverage area of the AP. Communicationslink 125 can comprise communications channels that can enable bothuplink and downlink communications. When connecting to an AP, an STA canfirst authenticate itself with the AP and then associate itself with theAP. Once associated, a communications link 125 may be establishedbetween the AP 105 and the STA 115 such that the AP 105 and theassociated STA 115 may exchange frames or messages through a directcommunications link 125. It should be noted that the wirelesscommunication system, in some examples, may not have a central AP (e.g.,AP 105), but rather may function as a peer-to-peer network between theSTAs (e.g., STA2 115-b and STA3 115-c over communication link 126).Accordingly, the functions of the AP 105 described herein mayalternatively be performed by one or more of the STAs 115.

While aspects of the present disclosure are described in connection witha WLAN deployment or the use of IEEE 802.11-compliant networks, thoseskilled in the art will readily appreciate, the various aspectsdescribed throughout this disclosure may be extended to other networksemploying various standards or protocols including, by way of example,BLUETOOTH® (Bluetooth), HiperLAN (a set of wireless standards,comparable to the IEEE 802.11 standards, used primarily in Europe), andother technologies used in wide area networks (WAN)s, WLANs, personalarea networks (PAN)s, or other suitable networks now known or laterdeveloped. Thus, the various aspects presented throughout thisdisclosure for performing operations based on modifications andenhancements to dynamic sensitivity control may be applicable to anysuitable wireless network regardless of the coverage range and thewireless access protocols utilized.

In some aspects, one or more APs (105-a and 105-b) may transmit on oneor more channels (e.g., multiple narrowband channels, each channelincluding a frequency bandwidth) a beacon signal (or simply a “beacon”),via a communications link 125 to STA(s) 115 of the wirelesscommunication system, which may help the STA(s) 115 to synchronize theirtiming with the APs 105, or which may provide other information orfunctionality. Such beacons may be transmitted periodically. In oneaspect, the period between successive transmissions may be referred toas a superframe. Transmission of a beacon may be divided into a numberof groups or intervals. In one aspect, the beacon may include, but isnot limited to, such information as timestamp information to set acommon clock, a peer-to-peer network identifier, a device identifier,capability information, a superframe duration, transmission directioninformation, reception direction information, a neighbor list, and/or anextended neighbor list, some of which are described in additional detailbelow. Thus, a beacon may include information that is both common (e.g.,shared) amongst several devices and specific to a given device.

In an aspect, a device (e.g., APs 105 and/or STAs 115) may include oneor more components for performing various functions described in thepresent disclosure. For example, the device (e.g., APs 105 and/or STAs115) may include a communication management component 405 (not shown—seee.g., FIG. 4) to perform procedures related to configuring the STAs byidentifying which of the one or more UL frame type associated withRTS/CTS protocol to use under which of one or more conditions. Moreover,the communication management component 405 may, for each one or more offrame types for UL transmissions associated with an RTS/CTS protocol,identify a different type of information to be included in the RTS/CTSmessages. In some examples, the communication management component 405may also identify one or more transmission parameter values for the STAto transmit each of the one or more frame types. Transmit parameter(s)may be transmission considerations applied by the STA in transmitting ULRTS/CTS protocol frames, including, but not limited to, a modulation andcoding scheme (MCS) index value, a bandwidth, a number of spatialstreams (NSS), a transmission power, enhanced distributed channel access(EDCA) parameters, and/or energy detection thresholds. In yet furtherexamples, the AP 105 may also identify one or more conditions fordisabling UL transmissions of RTS/CTS protocol at the STA 115. Forexample, if a transmission overhead parameter is less than apredetermined overhead threshold (i.e., overhead to transmit the ULpacket is less than the overhead required to transmit the RTS/CTSprotocol message), the AP 105 may configure the STA 115 to disable ULtransmission of the RTS/CTS protocol. For example, if the RTS/CTS frameduration is greater than ten percent (10%) of the TXOP duration, aspectsof the present disclosure may be configured to disable the ULtransmissions of RTS/CTS protocol. In another example, if the RTS/CTSframe duration is greater than fifty percent (50%) of the TXOP duration,aspects of the present disclosure may be configured to disable the ULtransmissions of RTS/CTS protocol.

By way of example, as noted above, RTS/CTS protocol messages may be usedto reduce data collisions between multiple STAs 115 transmitting uplinkmessages in a dense network. Specifically, an STA 115 that intends tosend data initiates a RTS frame to one (unicast) or more (multicast,broadcast) wireless devices (e.g., other STAs 115) indicating the intentto transmit data. The receiving STA 115 (or STAs) replies with a CTSframe, indicating that it is ready to receive the transmission. TheRTS/CTS frames also include information regarding a time period in whichany other wireless devices receiving the frames should not attempt toaccess the medium. However, in order to improve performance, aspects ofthe present disclosure allow the AP 105 to configure the one or moreSTAs to use different UL frame types based on varying conditions. Forexample, an AP1 105-a may configure STA1 115-a that is at the edge ofthe coverage area 110-a to use a legacy UL RTS/CTS frame type, whileconfiguring STA2 115-b that is closer to the AP 105-a to utilize amodified legacy UL RTS/CTS frame type. In some instances, the RTS frameis sent as part of an uplink (UL) transmission with a respective CTSframe response provided in a downlink (DL) transmission. In otherinstances, the CTS frame is sent as part of an UL transmission inresponse to a respective RTS frame provided in a DL transmission.

In some aspects, configuring the one or more STAs 115 may includetransmitting a configuration message from the AP 105 to the STA(s) 115.In one or more examples, the AP 105 may transmit differentconfigurations to different STA(s) 115. The configuration message mayinclude configuration information indicating the one or more frame typesand one or more conditions for the STA to use the one or more frametypes. In some examples, the one or more frame types in theconfiguration message may include an UL RTS frame type, an UL CTS frametype, or both. Additionally or alternatively, the one or more conditionsin the configuration message may include at least a first condition forusing the UL RTS frame type, at least a second condition for using theUL CTS frame type, or both.

The STA(s) 115, upon receiving the configuration message from the AP 105that includes configuration information indicating the one or more frametypes and one or more conditions for the STA to use the one or moreframe types, may configure itself based on the configuration informationprovided in the configuration message. Specifically, in some aspects,the STA 115 may update RTS/CTS frame type and revise one or more RTS/CTSparameter values based on configuration information received from the AP105. In some aspects, the AP1 105-a, for example, may configure each ofthe STAs 115 (e.g., STA1 115-a, STA2 115-b, and STA3 115-c) on a per-STAbasis. Thus, the AP1 105-a may transmit a first configuration messagethat includes information associated with one or more first frame typesto the first STA1 115-a, and transmit a second configuration messagethat includes information associated with one or more second frame typesfor a second STA2 115-b for UL transmission. In some examples, the oneor more second frame types for second STA2 115-b may be the same ordifferent RTS/CTS protocol than the RTS/CTS protocol associated with theUL transmission for the first STA1 115-a.

FIG. 1B is a conceptual diagram 104 illustrating an example of awireless local area network (WLAN) deployment in connection with varioustechniques described herein. The diagram 104 may include one or moreSTAs 115 described with reference to FIG. 1A.

In one or more examples, the STA(s) 115 may receive a configurationmessage from an AP 105. The configuration message may includeconfiguration information indicating the one or more frame types, one ormore conditions for the STA to use the one or more frame types and oneor more transmission parameter values for the STA to transmit with theone or more frame types. In some examples, the one or more frame typesin the configuration message may include an UL RTS frame type, an UL CTSframe type, or both. In one or more examples, transmit parameter(s) maybe transmission considerations applied by the STA in transmitting ULRTS/CTS protocol frames, including, but not limited to, a modulation andcoding scheme (MCS) index value, a bandwidth, a number of spatialstreams (NSS), a transmission power, enhanced distributed channel access(EDCA) parameters, a packet detection threshold and/or energy detectionthresholds.

Thus, upon receiving the configuration information from an AP 105, oneor more STAs 115 may modify the uplink transmissions associated withRTS/CTS protocol. For example, STA2 115-b, upon updating or modifyingthe parameter values associated with RTS/CTS protocol based on theconfiguration information received in a configuration message, maytransmit an UL RTS frame 132 to STA3 115-c prior to initiating datatransmission. The UL RTS frame 132 may be selected based on one or moreframe types identified from a plurality of frame types by the AP.Additionally or alternatively, the UL RTS frame 132 may be transmittedutilizing the transmission parameter values identified in theconfiguration information by the AP 105. In response, the STA2 115-b mayreceive a DL CTS frame 134 indicating whether the STA3 115-c isavailable to receive the data transmission.

Additionally or alternatively, the STA2 115-b may also transmit UL CTSframe 138 in accordance with aspects of the present disclosure inresponse to receiving a DL RTS 136 message from STA1 115-a. The UL CTSframe 138 structure may be based on the one or more frame typesidentified from a plurality of frame types by the AP 105. In someaspects, the UL CTS frame 138 may further be transmitted utilizing thetransmission parameter values (e.g., transmission power) identified bythe AP 105.

FIG. 2A is a flowchart conceptually illustrating an example of a method202 of wireless communication, in accordance with aspects of the presentdisclosure. For clarity, the method 202 is described below withreference to AP 105 described with reference to FIG. 1 and FIG. 4.

At 205, the method 202 may include identifying, at an AP, one or moreframe types for UL transmissions associated with a RTS/CTS protocol, theone or more frame types being identified from a plurality of frame typessupported by a STA for the UL transmissions. In some examples, the oneor more frame types may include, but are not limited to, legacy RTS/CTS,legacy RTS/CTS wrapped in control wrapper frame where the controlwrapper contains contents of legacy RTS/CTS, modified legacy RTS/CTSwith one or more bits redefined to carry new information. The one ormore frame types may further include directional multi-gigabit (DMG) CTSframe type, DMG CTS wrapped in control wrapper frame, a DMG CTS with oneor more bits redefined to carry new information, RTS/CTS with advanceddefined control frame subtype, or RTS/CTS for multi-user operation.Aspects of 205 may be performed by RTS/CTS protocol frame typeidentifier 410 described with reference to FIG. 4.

At 210, the method 202 may include transmitting a configuration messageto the STA. The configuration message may include configurationinformation indicating the one or more frame types, one or moreconditions for the STA to use the one or more frame types, one or moretypes of information for the STA to include in the one or more frametypes, and one or more transmission parameter values for the STA totransmit with the one or more frame types. Transmit parameter(s) may betransmission considerations applied by the STA in transmitting ULRTS/CTS protocol frames, including, but not limited to, a MCS indexvalue, a bandwidth, a NSS, a transmission power, EDCA parameters, and/orenergy detection thresholds. In some examples, the one or more frametypes in the configuration message include an UL RTS frame type, an ULCTS frame type, or both. Additionally or alternatively, the one or moreconditions in the configuration message include at least a firstcondition for using the UL RTS frame type, at least a second conditionfor using the UL CTS frame type, or both. In some examples, theconfiguration message may be included in one or more informationelements (IEs) of a frame (e.g., a management frame or beacon frame)transmitted from the AP 105. The AP 105 may broadcast, multicast, orunicast to the targeted device(s) (e.g., STAs 115) the frame having theone or more IEs. Aspects of 210 may be performed by STA configurationcomponent 420 and transceiver 402 described with reference to FIG. 4. Insome aspects, a type of information included in the one or more frametypes contains at least one or more types of information for spatialreuse by the STA, information for buffer status, information for linkadaptation, information for multi-user RTS/CTS operation, informationfor an operation mode, information for TXOP extension, or informationfor power saving.

In one or more examples, the one or more frame types in theconfiguration message may include a first frame type (selected from oneof the plurality of frame types identified above and supported by theSTA) for use as an UL CTS frame type to respond to a second frame typedifferent from the first frame type. For example, the STA(s) may beconfigured such that a responding STA may respond with legacy CTS inresponse to receiving legacy RTS. Conversely, in other examples, the STAmay transmit CTS with new control frame subtype in response to receivingRTS with new control frame subtype.

In yet further examples, the one or more frame types in theconfiguration message may include an UL RTS frame type configured to bedeferred by OBSS nodes. Thus, in some aspects, an OBSS node (e.g., STA4115-d in FIG. 1) that might hear an UL RTS frame transmitted by STA1115-a (see FIG. 1), may defer or drop the RTS message without respondingwith a corresponding CTS message.

In some aspects, the STA configuration component 420 may identify theone or more conditions in the configuration message that includes atleast one of the following conditions associated with using the UL RTSframe: (a) a received signal strength indication (RSSI) is less than aRSSI threshold, (b) a modulation and coding scheme (MCS) index value isless than a MCS threshold, (c) a PLCP protocol data unit (PPDU) durationis greater than a PPDU threshold, (d) a transmit opportunity (TXOP) isgreater than a TXOP threshold, (e) a PLCP service data unit (PSDU) sizeis greater than a PSDU size threshold, (f) a retransmission number isgreater than retry threshold, (g) a packet error rate (PER) is greaterthan PER threshold, (h) or an available bandwidth is greater thanbandwidth threshold. Thus, in some examples, the AP may configure STA touse legacy RTS if any one or more of the above-identified conditions aremet at the STA. With respect to the TXOP and the TXOP threshold,additional aspects are described below with respect to FIGS. 6-8B.

In yet further examples, the configuration information in theconfiguration message may further indicate a type of informationincluded in each of the one or more frame types. For example, the typeof information included in a first frame type of the one or more frametypes contains at least one or more of: (a) information for spatialreuse by the STA, (b) information for buffer status, (c) information forlink adaptation, (d) information for multi-user RTS/CTS protocolsincluding the RTS/CTS protocol, (e) information for an operation mode,(f) information for TXOP extension, or (g) information for power saving.

In some aspects, the information for spatial reuse by the STA mayinclude at last one of: (a) a transmit power of a frame sender, (b) amaximum allowed interference at the frame sender, (c) an indicator ofallowing OBSS nodes for frame dropping, (d) a packet detection levelrange for OBSS nodes for frame dropping, or (e) an indicator forinstructing the STA to drop OBSS frames. In some aspects, the AP 105 mayalso configure the STA 115 to utilize a specified value for parametersthat may be configurable. For instance, the AP 105 may configure the STAto utilize maximum allowed interference value to −80 Decibel-milliwatts(dBm), so that OBSS nodes may drop the received RTS/CTS if estimatedinterference to the RTS/CTS sender is less than −80 dBm. In otherexamples, the AP 105 may set the packet detection level range such thatOBSS nodes may drop the received RTS/CTS protocol message if the RSSIfalls less than −70 dBm.

In some examples, the information for buffer status by the STA mayinclude a buffer status (e.g., total size of the buffer or number ofqueued MPDUs) of a frame sender. In some aspects, the buffer statusinformation may include information regarding the total or per queue.Thus, when the STA 115 transmits an RTS/CTS protocol message, the STA115 may additionally include information regarding its buffer status forthe receiving device.

Similarly, information for link adaptation the STA may include at leastone of: (a) a channel quality indicator (CQI) at a frame sender, (b) asignal-to-interference-plus-noise (SINR) ratio at the frame sender, (c)an interference level at the frame sender, (d)

a recommended MCS for response frame, or (e) a statistic on one or moreof PER, delay, retry count, or busty interference occurrence.

In some aspects, the information for multi-user RTS/CTS protocols mayinclude a common scrambling seed. Thus, the AP 105 may configure each ofa plurality of STAs 115 in multi-user RTS/CTS protocol mode to utilize acommon frame type format when simultaneously sending RTS/CTS protocolmessages.

In yet further examples, the information for the operation mode for datatransmissions may include at least one of: (a) a modulation and codingscheme (MCS) index value, (b) a bandwidth, (c) an NSS, (d) atransmission power, (e) an acknowledgment policy, (f) a rate controlpolicy on bursty interference, or (g) an enhanced distributed channelaccess (EDCA) levels. In some aspects, the information for TXOPextension by the STA may include TXOP extension request/responseinformation. Additionally or alternatively, the information for powersaving by the STA may include sleep schedule request/responseinformation in the RTS/CTS messages.

FIG. 2B is a flowchart conceptually illustrating an example of a method204 of wireless communication, in accordance with another aspect of thepresent disclosure. For clarity, the method 204 is described below withreference to AP 105 described with reference to FIG. 1 and FIG. 4.

At 215, the method 204 may include identifying, at an AP, one or moreconditions for disabling UL transmissions of a RTS/CTS protocol at a STAassociated with the AP. The conditions for disabling UL transmissionsmay be different from the conditions described above with respect toFIG. 2A for the STA to use the one or more frame types. The one or moreconditions may include a condition in which a transmission overheadparameter is less than a predetermined overhead threshold. In someaspects, the transmission overhead parameter may be a PLCP protocol dataunit (PPDU) duration and the predetermined overhead threshold may be aPPDU threshold. Additionally or alternatively, the transmission overheadparameter may be a transmit opportunity (TXOP) parameter and thepredetermined overhead threshold may be a TXOP threshold.

In other examples, the one or more conditions may include a condition inwhich a link quality parameter is greater than a predetermined linkquality threshold. The link quality parameter may be a RSSI and thepredetermined link quality threshold is a RSSI threshold. Additionallyor alternatively, the link quality parameter may be a MCS index valueand the predetermined link quality threshold is a RSSI threshold.

In some aspects, identifying the one or more conditions may compriseidentifying a time window or channel in which to disable the ULtransmissions of the RTS/CTS protocol at the STA. Thus, a configurationmessage (at 220) may include configuration information indicating thetime window or channel in which to disable the UL transmissions of theRTS/CTS protocol.

In yet further examples, the one or more conditions may include acondition in which a collision parameter is less than a predeterminedcollision threshold. For example, the collision parameter may be a PERand the predetermined collision threshold may be a PER threshold.Additionally or alternatively, the collision parameter may be a numberof retransmissions and the predetermined collision threshold may be aretry threshold.

In one or more examples, identifying the one or more conditions maycomprise identifying a packet type or an access class for which todisable the UL transmissions of the RTS/CTS protocol at the STA. Thus, aconfiguration message may include a configuration information indicatingthe packet type or the access class of the STA. Aspects of 215 may beperformed by condition identification component 415 described withreference to FIG. 4.

FIG. 3A is a flowchart conceptually illustrating an example of a method300 of wireless communication, in accordance with aspects of the presentdisclosure. For clarity, the method 302 is described below withreference to STA 115 described with reference to FIG. 1 and FIG. 5.

At 305, the method 300 may include receiving, at a STA, a configurationmessage from an AP, the configuration message including configurationinformation indicating the one or more frame types, one or moreconditions for the STA to use the one or more frame type, and one ormore transmission parameter values for the STA to transmit with the oneor more frame types. Aspects of 305 may be performed by transceiver 502described with reference to FIG. 5.

At 310, the method 304 may include configuring the STA based on theconfiguration information provided in the configuration message. Aspectsof 305 may be performed by configuration component 505 described withreference to FIG. 5.

FIG. 3B is a flowchart conceptually illustrating an example of a method304 of wireless communication, in accordance with aspects of the presentdisclosure. For clarity, the method 304 is described below withreference to STA 115 described with reference to FIG. 1 and FIG. 5.

At 315, the method 304 may include receiving, at a STA, a configurationmessage from an AP, the configuration message includes configurationinformation indicating the one or more conditions for disabling ULtransmissions of a RTS/CTS protocol at the STA associated with the AP.Aspects of 305 may be performed by transceiver 502 described withreference to FIG. 5. Aspects of FIG. 3B may be performed by STA 115,memory 516 and/or processors 512, transceiver 502, configurationcomponent 505, RTX/CTX protocol component 510, and/or TXOP thresholdconfiguration component 425.

At 320, the method 304 may include configuring the STA based on theconfiguration information provided in the configuration message. Aspectsof 320 may be performed by configuration component 505 described withreference to FIG. 5.

FIG. 4 describes hardware components and subcomponents of the AP 105 forimplementing one or more methods (e.g., methods 202, 204, and 800)described herein in accordance with various aspects of the presentdisclosure. For example, one example of an implementation of AP 105 mayinclude a variety of components, some of which have already beendescribed above, but including components such as one or more processors412 and memory 416 and transceiver 402 in communication via one or morebuses 444, which may operate in conjunction with communicationmanagement component 405 to enable one or more of the functionsdescribed herein related to including one or more methods of the presentdisclosure. Further, the one or more processors 412, modem 414, memory416, transceiver 402, RF front end 488 and one or more antennas 465, maybe configured to support voice and/or data calls (simultaneously ornon-simultaneously) in one or more radio access technologies.

In an aspect, the one or more processors 412 can include a modem 414that uses one or more modem processors. The various functions related tocommunication management component 405 may be included in modem 414and/or processors 412 and, in an aspect, can be executed by a singleprocessor, while in other aspects, different ones of the functions maybe executed by a combination of two or more different processors. Forexample, in an aspect, the one or more processors 412 may include anyone or any combination of a modem processor, or a baseband processor, ora digital signal processor, or a transmit processor, or a receiverprocessor, or a transceiver processor associated with transceiver 402.In other aspects, some of the features of the one or more processors 412and/or modem 414 associated with communication management component 405may be performed by transceiver 402.

Also, memory 416 may be configured to store data used herein and/orlocal versions of applications or communication management component 405and/or one or more of its subcomponents being executed by at least oneprocessor 412. Memory 416 can include any type of computer-readablemedium usable by a computer or at least one processor 412, such asrandom access memory (RAM), read only memory (ROM), tapes, magneticdiscs, optical discs, volatile memory, non-volatile memory, and anycombination thereof. In an aspect, for example, memory 416 may be anon-transitory computer-readable storage medium that stores one or morecomputer-executable codes defining communication management component405 and/or one or more of its subcomponents, and/or data associatedtherewith, when AP 105 is operating at least one processor 412 toexecute communication management component 405 and/or one or more of itssubcomponents.

Transceiver 402 may include at least one receiver 406 and at least onetransmitter 408. Receiver 406 may include hardware, firmware, and/orsoftware code executable by a processor for receiving data, the codecomprising instructions and being stored in a memory (e.g.,computer-readable medium). Receiver 406 may be, for example, a radiofrequency (RF) receiver. In an aspect, receiver 406 may receive signalstransmitted by at least one STA 115. Additionally, receiver 406 mayprocess such received signals, and also may obtain measurements of thesignals, such as, but not limited to, Ec/Io, SNR, RSRP, RSSI, etc.Transmitter 408 may include hardware, firmware, and/or software codeexecutable by a processor for transmitting data, the code comprisinginstructions and being stored in a memory (e.g., computer-readablemedium). A suitable example of transceiver 402 may including, but is notlimited to, an RF transmitter.

Moreover, in an aspect, AP 105 may include RF front end 488, which mayoperate in communication with one or more antennas 465 and transceiver402 for receiving and transmitting radio transmissions, for example,wireless communications transmitted by at least one STA 115 or wirelesstransmissions transmitted by AP 105. RF front end 488 may be connectedto one or more antennas 465 and can include one or more low-noiseamplifiers (LNAs) 490, one or more switches 492, one or more poweramplifiers (PAs) 498, and one or more filters 496 for transmitting andreceiving RF signals.

In an aspect, LNA 490 can amplify a received signal at a desired outputlevel. In an aspect, each LNA 490 may have a specified minimum andmaximum gain values. In an aspect, RF front end 488 may use one or moreswitches 492 to select a particular LNA 490 and its specified gain valuebased on a desired gain value for a particular application.

Further, for example, one or more PA(s) 498 may be used by RF front end488 to amplify a signal for an RF output at a desired output powerlevel. In an aspect, each PA 498 may have specified minimum and maximumgain values. In an aspect, RF front end 488 may use one or more switches492 to select a particular PA 498 and its specified gain value based ona desired gain value for a particular application.

Also, for example, one or more filters 496 can be used by RF front end488 to filter a received signal to obtain an input RF signal. Similarly,in an aspect, for example, a respective filter 496 can be used to filteran output from a respective PA 498 to produce an output signal fortransmission. In an aspect, each filter 496 can be connected to aspecific LNA 490 and/or PA 498. In an aspect, RF front end 488 can useone or more switches 492 to select a transmit or receive path using aspecified filter 496, LNA 490, and/or PA 498, based on a configurationas specified by transceiver 402 and/or processor 412.

As such, transceiver 402 may be configured to transmit and receivewireless signals through one or more antennas 465 via RF front end488-a. In an aspect, transceiver may be tuned to operate at specifiedfrequencies such that AP 105 can communicate with, for example, one ormore STAs 115 or one or more cells associated with one or more APs 105.In an aspect, for example, modem 414 can configure transceiver 402 tooperate at a specified frequency and power level based on the APconfiguration of the AP 105 and the communication protocol used by modem414.

In an aspect, modem 414 can be a multiband-multimode modem, which canprocess digital data and communicate with transceiver 402 such that thedigital data is sent and received using transceiver 402. In an aspect,modem 414 can be multiband and be configured to support multiplefrequency bands for a specific communications protocol. In an aspect,modem 414 can be multimode and be configured to support multipleoperating networks and communications protocols. In an aspect, modem 414can control one or more components of AP 105 (e.g., RF front end 488,transceiver 402) to enable transmission and/or reception of signals fromthe network based on a specified modem configuration. In an aspect, themodem configuration can be based on the mode of the modem and thefrequency band in use. In another aspect, the modem configuration can bebased on AP configuration information associated with AP 105 as providedby the network during cell selection and/or cell reselection.

In some examples, the communication management component 405 may includea RTS/CTS protocol frame type identifier 410 for identifying, at an AP,one or more frame types for UL transmissions associated with RTS/CTSprotocol, the one or more frame types being identified from a pluralityof frame types supported by a STA for the UL transmissions as describedwith reference to FIG. 2. The RTS/CTS protocol frame type identifier 410may comprise hardware, firmware, and/or software and may be configuredto execute code or perform instructions stored in a memory (e.g., acomputer-readable storage medium). The communication managementcomponent 405 may further include a condition identification component415 for identifying a identifying, at an AP, one or more conditions fordisabling UL transmissions of a RTS/CTS protocol at a STA associatedwith the AP. The communication management component 405 may comprisehardware, firmware, and/or software and may be configured to executecode or perform instructions stored in a memory (e.g., acomputer-readable storage medium).

Additionally or alternatively, the communication management component405 may include an STA configuration component 420 configured togenerate configuration messages for transmission by the transceiver 402.The STA configuration component 420 may comprise hardware, firmware,and/or software and may be configured to execute code or performinstructions stored in a memory (e.g., a computer-readable storagemedium). In some aspects, the configuration message may includeconfiguration information indicating the one or more frame types, one ormore conditions for the STA to use the one or more frame types, and oneor more transmission parameter values for the STA to transmit with eachof the one or more frame types.

Additionally or alternatively, the communication management component405 may include a TXOP threshold configuration component 425 configuredto perform the various functions described below with respect to TXOPthreshold broadcasting/unicasting and TXOP threshold overwriting, asperformed by an AP (see e.g., FIGS. 6, 7, and 8A). The TXOP thresholdconfiguration component 425 may comprise hardware, firmware, and/orsoftware and may be configured to execute code or perform instructionsstored in a memory (e.g., a computer-readable storage medium).

FIG. 5 describes hardware components and subcomponents of the STA 115for implementing one or more methods (e.g., methods 302, 304, and 820)described herein in accordance with various aspects of the presentdisclosure. For example, one example of an implementation of STA 115 mayinclude a variety of components, some of which have already beendescribed above, but including components such as one or more processors512 and memory 516 and transceiver 502 in communication via one or morebuses 544, which may operate in conjunction with configuration component505 to enable one or more of the functions described herein related toincluding one or more methods of the present disclosure. Further, theone or more processors 512, modem 514, memory 516, transceiver 502, RFfront end 588 and one or more antennas 565, may be configured to supportvoice and/or data calls (simultaneously or non-simultaneously) in one ormore radio access technologies.

In an aspect, the one or more processors 512 can include a modem 514that uses one or more modem processors. The various functions related toconfiguration component 505 may be included in modem 514 and/orprocessors 512 and, in an aspect, can be executed by a single processor,while in other aspects, different ones of the functions may be executedby a combination of two or more different processors. For example, in anaspect, the one or more processors 512 may include any one or anycombination of a modem processor, or a baseband processor, or a digitalsignal processor, or a transmit processor, or a receiver processor, or atransceiver processor associated with transceiver 502. In other aspects,some of the features of the one or more processors 512 and/or modem 514associated with configuration component 505 may be performed bytransceiver 502.

Also, memory 516 may be configured to store data used herein and/orlocal versions of applications or configuration component 505 and/or oneor more of its subcomponents being executed by at least one processor512. Memory 516 can include any type of computer-readable medium usableby a computer or at least one processor 512, such as random accessmemory (RAM), read only memory (ROM), tapes, magnetic discs, opticaldiscs, volatile memory, non-volatile memory, and any combinationthereof. In an aspect, for example, memory 516 may be a non-transitorycomputer-readable storage medium that stores one or morecomputer-executable codes defining configuration component 505 and/orone or more of its subcomponents, and/or data associated therewith, whenSTA 115 is operating at least one processor 512 to execute configurationcomponent 505 and/or one or more of its subcomponents.

Transceiver 502 may include at least one receiver 506 and at least onetransmitter 508. Receiver 506 may include hardware, firmware, and/orsoftware code executable by a processor for receiving data, the codecomprising instructions and being stored in a memory (e.g.,computer-readable medium). Receiver 506 may be, for example, a radiofrequency (RF) receiver. In an aspect, receiver 506 may receive signalstransmitted by at least one AP 105. Additionally, receiver 506 mayprocess such received signals, and also may obtain measurements of thesignals, such as, but not limited to, Ec/Io, SNR, RSRP, RSSI, etc.Transmitter 508 may include hardware, firmware, and/or software codeexecutable by a processor for transmitting data, the code comprisinginstructions and being stored in a memory (e.g., computer-readablemedium). A suitable example of transceiver 502 may including, but is notlimited to, an RF transmitter.

Moreover, in an aspect, STA 115 may include RF front end 588, which mayoperate in communication with one or more antennas 565 and transceiver502 for receiving and transmitting radio transmissions, for example,wireless communications transmitted by at least one AP 105 or wirelesstransmissions transmitted by STA 115. RF front end 588 may be connectedto one or more antennas 565 and can include one or more low-noiseamplifiers (LNAs) 590, one or more switches 592, one or more poweramplifiers (PAs) 598, and one or more filters 596 for transmitting andreceiving RF signals.

In an aspect, LNA 590 can amplify a received signal at a desired outputlevel. In an aspect, each LNA 590 may have a specified minimum andmaximum gain values. In an aspect, RF front end 588 may use one or moreswitches 592 to select a particular LNA 590 and its specified gain valuebased on a desired gain value for a particular application.

Further, for example, one or more PA(s) 598 may be used by RF front end588 to amplify a signal for an RF output at a desired output powerlevel. In an aspect, each PA 598 may have specified minimum and maximumgain values. In an aspect, RF front end 588 may use one or more switches592 to select a particular PA 598 and its specified gain value based ona desired gain value for a particular application.

Also, for example, one or more filters 596 can be used by RF front end588 to filter a received signal to obtain an input RF signal. Similarly,in an aspect, for example, a respective filter 596 can be used to filteran output from a respective PA 598 to produce an output signal fortransmission. In an aspect, each filter 596 can be connected to aspecific LNA 590 and/or PA 598. In an aspect, RF front end 588 can useone or more switches 592 to select a transmit or receive path using aspecified filter 596, LNA 590, and/or PA 598, based on a configurationas specified by transceiver 502 and/or processor 512.

As such, transceiver 502 may be configured to transmit and receivewireless signals through one or more antennas 565 via RF front end 588.In an aspect, transceiver may be tuned to operate at specifiedfrequencies such that STA 115 can communicate with, for example, one ormore other STA 115 or one or more cells associated with one or more APs105. In an aspect, for example, modem 514 can configure transceiver 502to operate at a specified frequency and power level based on the STAconfiguration of the STA 115 and the communication protocol used bymodem 514.

In an aspect, modem 514 can be a multiband-multimode modem, which canprocess digital data and communicate with transceiver 502 such that thedigital data is sent and received using transceiver 502. In an aspect,modem 514 can be multiband and be configured to support multiplefrequency bands for a specific communications protocol. In an aspect,modem 514 can be multimode and be configured to support multipleoperating networks and communications protocols. In an aspect, modem 514can control one or more components of STA 115 (e.g., RF front end 588,transceiver 502) to enable transmission and/or reception of signals fromthe network based on a specified modem configuration. In an aspect, themodem configuration can be based on the mode of the modem and thefrequency band in use. In another aspect, the modem configuration can bebased on STA configuration information associated with STA 115 asprovided by the network during cell selection and/or cell reselection.

In some aspects, the transceiver 502 may receive a configuration messagefrom an AP. The transceiver 502 may aid in decoding the configurationmessage. In some aspects, the configuration message may indicate the oneor more frame types and one or more conditions for the STA 115 to usethe one or more frame types. Additionally or alternatively, the receivedconfiguration message may include configuration information indicatingthe one or more conditions for disabling UL transmissions of a RTS/CTSprotocol at the STA associated with the AP. In one or more examples, theconfiguration component 505 may be configure the STA 115 based on theconfiguration information provided in the configuration message. Forexample, configuring the STA 115 may include revising or updating one ormore RTS/CTS parameters at the RTX/CTX protocol component 510. In otherwords, configuration information may be stored in the RTX/CTX protocolcomponent 510 and appropriate RTS/CTS parameters may be updated based onconfiguration information so that the correct frame types are used basedon conditions observed at the STA 115.

Additionally or alternatively, the configuration component 505 mayinclude a TXOP threshold component 515 configured to perform the variousfunctions described below with respect to receiving TXOP thresholdbroadcasting/unicasting and TXOP threshold overwriting, as performed byan STA (see e.g., FIGS. 6, 7, and 8B). The TXOP threshold component 515may comprise hardware, firmware, and/or software and may be configuredto execute code or perform instructions stored in a memory (e.g., acomputer-readable storage medium). Moreover, aspects of the TXOPthreshold component 515 may operate in conjunction with aspects ofRTX/CTX protocol component 510, and in some examples, TXOP thresholdcomponent 515 may be implemented at least partially in RTX/CTX protocolcomponent 510.

As described above, an AP can be used to control UL RTS/CTS operationsin an STA. That is, various aspects described above provide formechanisms or techniques that allow an AP to configure the use ofRTS/CTS initiated by a non-AP STA. As such, different criteria andsignaling for RTS/CTS configuration are provided in this disclosure,with further aspects described below.

For example, aspects of this disclosure provide for TXOP-based ULRTS/CTS enablement. That is, an AP (e.g., AP 105) may signal, transmit,or otherwise indicate a ‘TXOP duration’ threshold, sometimes simplyreferred to as a TXOP threshold, to one or more STAs in the BSS of theAP. An STA (e.g., STA 115) that receives the indication of the TXOPthreshold from the AP and that obtains a TXOP, may then start the TXOPby sending RTS (e.g., RTS frame) if the planned TXOP duration satisfies(e.g., exceeds) the TXOP threshold. This approach, however, need notprevent other implementations in which additional conditions are definedfor having an STA transmit RTS/CTS. For example, an STA may determine ordecide to send RTS when the planned TXOP duration does not satisfy theTXOP threshold (e.g., TXOP<TXOP threshold) when other considerations aretaken into account.

In some aspects, TXOP may be a useful metric because it is a moregeneral metric to quantify the overhead presented by RTS/CTS. Forexample, if overhead is small, RTS/CTS may be useful in improvingprotection from hidden nodes and CSMA collisions at negligible cost. Insome instances, PSDU and TXTIME are considered as examples of metrics toquantify overhead. However, the size of PSDU need not reflect the actualtransmission time (e.g., if rates are higher the time of PSDUtransmission is shorter. Moreover, TXTIM is not clearly defined in caseof multiple frame exchanges in TXOP protected by RTS/CTS. TXOP, as notedabove, may be a better metric or parameter to quantify overhead becausean STA may have UL data bursts or mixed UL and DL frames in TXOP (e.g.,reverse direction grant (RDG) initiated by STA, power save poll(PS-poll) and DL data).

FIG. 6 shows a chart 600 illustrating an example RTS/CTS overhead as afunction of TXOP. In chart 600, RTS/CTS overhead percentage (%) is shownas a function of TXOP, where overhead is defined as RTS/CTS durations inaddition to 2×SIFS. For example, RTS duration may be 52 μs, while CTSduration may be 44 μs. The results shown in chart 600, which clearlyillustrate the reduction of RTS/CTS overheard with increasing TXOPduration, are based on the following conditions: 6 Mbps, 20 μs preamble,16 service bits, and 6 tail bits.

FIG. 7 shows a block diagram 700 illustrating a control informationelement (IE) in accordance with various aspects of present disclosure.The control IE in diagram 700 may refer to an UL RTS/CTS control IE,which may be used by an AP to signal or convey TXOP thresholds. Asshown, the control IE may include various portions or fields. A firstportion or field may be the element identifier (ID), which may involve,for example, one octet. A second portion or field may be the length,which may involve, for example, one octet. A third portion or field maybe the TXOP threshold, which may involve, for example, two octets. Thecontrol IE, its size, and the various portions, fields, or sectionsshown in FIG. 7 are provided by way of illustration and not oflimitation. Also included in any one of the portions shown, or in adifferent portion, may be an indication of whether a STA receiving thecontrol IE is to replace or overwrite its current TXOP threshold withthe one in the control IE. As described in more detail below, suchindication may be a single common bit that is set or a bit in a bitmapthat is set.

In an aspect related to the control IE shown in FIG. 7, in one case, theAP can configure an STA to enable RTS in each instance by simply settingthe TXOP threshold to zero (“0”) such that a planned TXOP durationgreater than zero will always trigger the sending of RTS.

In another aspect, an AP may broadcast a TXPO threshold to multiple STAsor may transmit TXOP thresholds on a per-STA basis (e.g., unicasttransmissions). Accordingly, a mechanism or technique is needed toindicate if a broadcast TXOP threshold is to overwrite or replace acurrent or per-STA TXOP threshold, or if a per-STA TXOP threshold is tooverwrite or replace a current broadcast TXOP threshold. When, forexample, a control IE such as the one in FIG. 7 is broadcast by an AP,the control IE may include an “overwrite” bit that is added to indicateif an STA receiving the control IE is to overwrite or replace a currentper-STA TXOP threshold (e.g., one previously provided as a per-STA TXOPthreshold to that particular STA) with the TXOP threshold that is partof the broadcast control IE. For example, a single bit may be used forall STAs such that when such single bit is set, a common overwrite orreplace indication is provided to all the STAs. In another example, abit can be used on a per-STA basis by having the AP signal a bitmap witheach bit in the bitmap corresponding to an STA's association ID (AID).In such an example, each bit that is set in the bitmap would indicate toits corresponding STA to overwrite or replace the STA's current TXOPthreshold with the TXOP threshold in the control IE.

FIG. 8A is a flowchart of another example method of wirelesscommunication implemented on an AP in accordance with various aspects ofthe present disclosure. Aspects of FIG. 8A may be performed by AP 105,memory 416 and/or processors 412, transceiver 402, communicationmanagement component 405, and/or TXOP threshold configuration component425.

At block 805 of method 800, an AP (e.g., AP 105) may determine a TXOPthreshold for an STA (e.g., STA 115). In some examples, aspects of block805 may be performed by TXOP threshold configuration component 425described with reference to FIG. 4.

At block 810 of method 800, the AP may determine whether to broadcast amessage (e.g., a message including a control IE as shown in FIG. 7)having the TXOP threshold to one or more STAs including the STA, or tounicast the message having the TXOP threshold to the STA.

At block 815 of method 800, the AP may transmit (e.g., via transceiver402) the message according to the determination of whether to broadcastthe message or unicast the message.

In another aspect of method 800, the AP may transmit an indication toreplace a current TXOP threshold with the TXOP threshold in the message.In one example, transmitting the message includes broadcasting themessage and the indication is a single bit in the broadcast message thatis a common indication for each of the one or more STAs to replace acurrent TXOP threshold with the TXOP threshold in the broadcast message.In another example, transmitting the message includes broadcasting themessage and the indication is a bitmap in the broadcast message whereeach set bit in the bitmap identifies a respective one of the one ormore STAs for which the current TXOP threshold is to be replaced withthe TXOP threshold in the broadcast message.

In another aspect of method 800, transmitting the message includesunicasting the message to the STA and a current TXOP threshold in theSTA is a previously broadcast TXOP threshold to be replaced with theTXOP threshold in the unicast message.

In another aspect of method 800, the message includes an UL RTS/CTScontrol IE having the TXOP threshold.

FIG. 8B is a flowchart of another example method of wirelesscommunication implemented on an STA in accordance with various aspectsof the present disclosure. Aspects of FIG. 8B may be performed by STA115, memory 516 and/or processors 512, configuration component 505,and/or TXOP threshold component 515.

At block 825 of method 820, an STA (e.g., STA 115) may receive from anAP (e.g., AP 105) a message having a TXOP threshold.

At block 830 of method 820, the STA may replace or overwrite, based onan indication in the message received from the AP, a current TXOPthreshold in the STA with the TXOP threshold in the received message.

At block 835 of method 820, the STA may determine that a planned TXOPduration satisfies (e.g., exceeds) the TXOP threshold.

At block 840 of method 820, the STA may transmit (e.g. via transceiver502), a UL RTS frame in response to the determination that the plannedTXOP duration satisfies the TXOP threshold.

In another aspect of method 820, the message is a broadcast message fromthe AP, and the indication is a single bit in the broadcast message thatis a common indication to replace the current TXOP threshold with theTXOP threshold in the broadcast message.

In another aspect of method 820, the message is a broadcast message fromthe AP, and the indication is a bitmap in the broadcast message whereone set bit in the bitmap identifies the STA as an STA for which thecurrent TXOP threshold is to be replaced with the TXOP threshold in thebroadcast message.

In another aspect of method 820, the message is a unicast message andthe current TXOP threshold in the STA is a previously broadcast TXOPthreshold to be replaced with the TXOP threshold in the unicast message.In another aspect of method 820, the message includes an UL RTS/CTScontrol IE having the TXOP threshold.

FIG. 9 is a flowchart conceptually illustrating an example of a method900 of wireless communication, in accordance with another aspect of thepresent disclosure. For clarity, the method 900 is described below withreference to AP 105 described with reference to FIG. 1 and FIG. 4. Insome examples, the method 900 may incorporate aspects of the methodsdescribed with reference to FIGS. 2B and 8A in whole or in part.

At 905, the method may include identifying, at an AP, one or moreconditions for one or more of disabling or enabling UL transmissions ofa RTS/CTS protocol at a STA associated with the AP. Aspects of 905 maybe performed by condition identification component 415 described withreference to FIG. 4.

In some examples, the conditions for disabling UL transmissions of theRTS/CTS protocol may include a disabling condition in which atransmission overhead parameter is less than a predetermined overheadthreshold. In some aspects, the transmission overhead parameter may be aPPDU duration and the predetermined overhead threshold may be a PPDUthreshold. Additionally or alternatively, the transmission overheadparameter may be a TXOP parameter and the predetermined overheadthreshold may be a TXOP threshold. In other examples, the one or moreconditions may include a disabling condition in which a link qualityparameter is greater than a predetermined link quality threshold. Thelink quality parameter may be a RSSI and the predetermined link qualitythreshold is a RSSI threshold. Additionally or alternatively, the linkquality parameter may be a MCS index value and the predetermined linkquality threshold is a RSSI threshold.

In some aspects, identifying the one or more conditions may compriseidentifying a time window or channel in which to disable the ULtransmissions of the RTS/CTS protocol at the STA. Thus, a configurationmessage (at 925) may include configuration information indicating thetime window or channel in which to disable the UL transmissions of theRTS/CTS protocol. In yet further examples, the one or more conditionsmay include a disabling condition in which a collision parameter is lessthan a predetermined collision threshold. For example, the collisionparameter may be a PER and the predetermined collision threshold may bea PER threshold. Additionally or alternatively, the collision parametermay be a number of retransmissions and the predetermined collisionthreshold may be a retry threshold. In one or more examples, identifyingthe one or more conditions may comprise identifying a packet type or anaccess class for which to disable the UL transmissions of the RTS/CTSprotocol at the STA. Thus, a configuration message may include aconfiguration information indicating the packet type or the access classof the STA.

Additionally or alternatively, the conditions for enabling ULtransmissions of the RTS/CTS protocol may include setting, at the AP, aTXOP threshold for the STA. In some examples, the STA determines aplanned TXOP duration satisfies the TXOP threshold set by the AP in itsconsideration of whether to enable RTS/CTS protocol. In some aspects,the STA may start the TXOP by sending an RTS if the planned TXOPduration exceeds the TXOP threshold. Alternatively, the STA may cease toenable the RTS/CTS protocol when the planned TXOP duration is less thanthe TXOP threshold. Accordingly, in an some aspects, the method mayoptionally at 915 may include determining a TXOP threshold for the STA.In some examples, aspects of block 925 may be performed by TXOPthreshold configuration component 425 described with reference to FIG.4.

At 920, the method may optionally include determining whether tobroadcast a message having the TXOP threshold to one or more STAsincluding the STA or to unicast the message to the STA. Aspects of block920 may be performed by the transceiver 402 described with reference toFIG. 4.

At 925, the method may include transmitting a configuration message tothe STA. The configuration message may include configuration informationindicating the one or more conditions. As noted above, in some examples,the one or more conditions may identify the conditions that may identifywhen the STA should enable or disable the UL transmission of RTS/CTS. Inone or more examples, the AP may either broadcast or unicast theconfiguration message based on the determining step of 920. Aspects of925 may also be performed by the transceiver 402 described withreference to FIG. 4.

FIG. 9B is a flowchart conceptually illustrating an example of a method950 of wireless communication, in accordance with aspects of the presentdisclosure. For clarity, the method 950 is described below withreference to STA 115 described with reference to FIG. 1 and FIG. 5. Insome examples, the method 950 may incorporate, in whole or in part,aspects of the methods 304 and 820 described with reference to FIGS. 3Band 8B respectively.

At 930, the method may include receiving, at a STA, a configurationmessage from an AP, the configuration message includes configurationinformation indicating the one or more conditions for disabling orenabling UL transmissions of a RTS/CTS protocol at the STA associatedwith the AP. Aspects of 930 may be performed by transceiver 502described with reference to FIG. 5.

At 935, the method may include configuring the STA based on theconfiguration information provided in the configuration message. Aspectsof 935 may be performed by configuration component 505 described withreference to FIG. 5.

At block 940 of method, the STA may replace or overwrite, based on anindication in the configuration message received from the AP, a currentTXOP threshold in the STA with the TXOP threshold in the receivedmessage. Aspects of 940 may be performed by TXOP threshold component 515described with reference to FIG. 5.

At block 945 of method, the STA may determine that a planned TXOPduration satisfies (e.g., exceeds) the TXOP threshold. Aspects of 945may also be performed by TXOP threshold component 515 described withreference to FIG. 5.

At block 950 of method, the STA may transmit, an UL RTS frame inresponse to the determination that the planned TXOP duration satisfiesthe TXOP threshold. Aspects of block 950 may be performed by transceiver502 described with reference to FIG. 5. The apparatus and methods havebeen described in the detailed description and illustrated in theaccompanying drawings by various elements comprising blocks, modules,components, circuits, steps, processes, algorithms, and the like. Theseelements, or any portion thereof, either alone or in combinations withother elements and/or functions, may be implemented using electronichardware, computer software, or any combination thereof. Whether suchelements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. In an aspect, the term “component” as used herein may be one ofthe parts that make up a system and may be divided into othercomponents.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented with a “processing system”that includes one or more processors. A processor may include a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic component, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof, or any other suitable component designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computingcomponents, e.g., a combination of a DSP and a microprocessor, aplurality of microprocessors, one or more microprocessors in conjunctionwith a DSP, or any other such configuration.

One or more processors in the processing system may execute software.Software shall be construed broadly to mean instructions, instructionsets, code, code segments, program code, programs, subprograms, softwaremodules, applications, software applications, software packages,routines, subroutines, objects, executables, threads of execution,procedures, functions, etc., whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise. Thesoftware may reside on transitory or non-transitory computer-readablemedium. A non-transitory computer-readable medium may include, by way ofexample, a magnetic storage device (e.g., hard disk, floppy disk,magnetic strip), an optical disk (e.g., compact disk (CD), digitalversatile disk (DVD)), a smart card, a flash memory device (e.g., card,stick, key drive), random access memory (RAM), static RAM (SRAM),dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM); double date rateRAM (DDRAM), read only memory (ROM), programmable ROM (PROM), erasablePROM (EPROM), electrically erasable PROM (EEPROM), a general register,or any other suitable non-transitory medium for storing software.

The various interconnections within a processing system may be shown asbuses or as single signal lines. Each of the buses may alternatively bea single signal line, and each of the single signal lines mayalternatively be buses, and a single line or bus might represent any oneor more of a myriad of physical or logical mechanisms for communicationbetween elements. Any of the signals provided over various busesdescribed herein may be time-multiplexed with other signals and providedover one or more common buses.

The various aspects of this disclosure are provided to enable one ofordinary skill in the art to practice the present invention. Variousmodifications to examples of implementations presented throughout thisdisclosure will be readily apparent to those skilled in the art, and theconcepts disclosed herein may be extended to other magnetic storagedevices. Thus, the claims are not intended to be limited to the variousaspects of this disclosure, but are to be accorded the full scopeconsistent with the language of the claims. All structural andfunctional equivalents to the various components of the examples ofimplementations described throughout this disclosure that are known orlater come to be known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the claims. Moreover, nothing disclosed herein isintended to be dedicated to the public regardless of whether suchdisclosure is explicitly recited in the claims. No claim element is tobe construed under the provisions of 35 U.S.C. § 112(f), unless theelement is expressly recited using the phrase “means for” or, in thecase of a method claim, the element is recited using the phrase “stepfor.”

What is claimed is:
 1. A method for wireless communications, comprising:identifying, at an access point (AP), one or more frame types for uplink(UL) transmissions from a station (STA) that are to be used as part of arequest-to-send/clear-to-send (RTS/CTS) protocol, the one or more frametypes being identified from a plurality of frame types supported by theSTA for the UL transmissions of the RTS/CTS protocol; and transmitting aconfiguration message to the STA, the configuration message includingconfiguration information to configure the UL transmissions of theRTS/CTS protocol in the STA, the configuration information indicatingthe one or more frame types, one or more conditions for the STA to usethe one or more frame types, and one or more transmission parametervalues for the STA to transmit with the one or more frame types.
 2. Themethod of claim 1, wherein: the one or more frame types in theconfiguration message include an UL RTS frame type, an UL CTS frametype, or both, and the one or more conditions in the configurationmessage include at least a first condition for using the UL RTS frametype, at least a second condition for using the UL CTS frame type, orboth.
 3. The method of claim 2, wherein the UL RTS frame type and theCTS frame type include at least one of: a legacy RTS frame or a legacyCTS frame, a legacy RTS frame or a legacy CTS frame wrapped in controlwrapper frame, a legacy RTS frame or a legacy CTS frame with one or morebits redefined to carry new information, a RTS frame or a legacy CTSframe with advanced control frame subtype, or a RTS frame or a legacyCTS frame for multi-user operation.
 4. The method of claim 2, whereinthe CTS frame type include at least one of: a Directional Multi-Gigabit(DMG) CTS frame type, a DMG CTS wrapped in control wrapper frame, a DMGCTS with one or more bits redefined to carry new information.
 5. Themethod of claim 1, wherein the one or more frame types in theconfiguration message include a first frame type for use as an UL CTSframe type to respond to a second frame type different from the firstframe type.
 6. The method of claim 1, wherein the one or more frametypes in the configuration message include an UL RTS frame typeconfigured to be deferred by overlapping basic service set (OBSS) nodes.7. The method of claim 1, wherein the one or more conditions in theconfiguration message include at least one of the following conditionsassociated with using the UL RTS frame: a received signal strengthindication (RSSI) is less than a RSSI threshold, a modulation and codingscheme (MCS) index value is less than a MCS threshold, a PLCP protocoldata unit (PPDU) duration is greater than a PPDU threshold, a transmitopportunity (TXOP) is greater than a TXOP threshold, a PLCP service dataunit (PSDU) size is greater than a PSDU size threshold, a retransmissionnumber is greater than a retry threshold, a packet error rate (PER) isgreater than a PER threshold, or an available bandwidth is greater thana bandwidth threshold.
 8. The method of claim 1, wherein theconfiguration information in the configuration message further indicatesa type of information included in each of the one or more frame types.9. The method of claim 8, wherein the type of information included in afirst frame type of the one or more frame types contains at least one ormore of: information for spatial reuse by the STA, information forbuffer status, information for link adaptation, information formulti-user RTS/CTS operation, information for an operation mode,information for TXOP extension, or information for power saving.
 10. Themethod of claim 9, wherein the information for spatial reuse by the STAincludes at least one of: a transmit power of a frame sender, a maximumallowed interference at the frame sender, an indicator of allowing OBSSnodes for frame dropping, a packet detection level range for OBSS nodesfor frame dropping, or an indicator for instructing the STA to drop OBSSframes.
 11. The method of claim 9, wherein the information for bufferstatus by the STA includes a buffer status of a frame sender.
 12. Themethod of claim 9, wherein the information for link adaptation by theSTA includes at least one of: a channel quality indicator (CQI) at aframe sender, a signal-to-interference-plus-noise (SINR) ratio at theframe sender, an interference level at the frame sender, a recommendedMCS for response frame, or statistics on one or more of PER, delay,retry count, or busty interference occurrence.
 13. A method for wirelesscommunication, comprising: receiving, at a station (STA), aconfiguration message from an access point (AP), the configurationmessage including configuration information to configure uplink (UL)transmissions to be used by the STA as part of arequest-to-send/clear-to-send (RTS/CTS) protocol, the configurationinformation indicating one or more frame types from a plurality of frametypes supported by the STA for the UL transmissions of the RTS/CTSprotocol, one or more conditions for the STA to use the one or moreframe types, and one or more transmission parameter values for the STAto transmit with the one or more frame types; configuring the STA basedon the configuration information provided in the configuration message;and performing, by the configured STA, the UL transmissions of theRTS/CTS protocol.
 14. The method of claim 13, wherein: the one or moreframe types in the configuration message include an UL RTS frame type,an UL CTS frame type, or both, and the one or more conditions in theconfiguration message include at least a first condition for using theUL RTS frame type, at least a second condition for using the UL CTSframe type, or both.
 15. The method of claim 13, wherein the one or moreframe types in the configuration message include a first frame type foruse as an UL CTS frame type to respond to a second frame type differentfrom the first frame type.
 16. The method of claim 13, wherein the oneor more frame types in the configuration message include an UL RTS frametype configured to be deferred by overlapping basic service set (OBSS)nodes.
 17. The method of claim 13, wherein the one or more conditions inthe configuration message include at least one of the followingconditions associated with using the UL RTS frame: a received signalstrength indication (RSSI) is less than a RSSI threshold, a modulationand coding scheme (MCS) index value is less than a MCS threshold, a PLCPprotocol data unit (PPDU) duration is greater than a PPDU threshold, atransmit opportunity (TXOP) is greater than a TXOP threshold, a PLCPservice data unit (PSDU) size is greater than a PSDU size threshold, aretransmission number is greater than a retry threshold, a packet errorrate (PER) is greater than a PER threshold, or an available bandwidth isgreater than a bandwidth threshold.
 18. The method of claim 13, whereinthe configuration information in the configuration message furtherindicates a type of information included in each of the one or moreframe types.
 19. An apparatus for wireless communication, comprising: aprocessor; and a memory coupled to the processor, wherein the memoryincludes instructions executable by the processor to: identify, at anaccess point (AP), one or more frame types for uplink (UL) transmissionsfrom a station (STA) that are to be used as part of arequest-to-send/clear-to-send (RTS/CTS) protocol, the one or more frametypes being identified from a plurality of frame types supported by theSTA for the UL transmissions of the RTS/CTS protocol; and transmit aconfiguration message to the STA, the configuration message includingconfiguration information to configure the UL transmissions of theRTS/CTS protocol in the STA, the configuration information indicatingthe one or more frame types, one or more conditions for the STA to usethe one or more frame types, and one or more transmission parametervalues for the STA to transmit with the one or more frame types.
 20. Theapparatus of claim 19, wherein: the one or more frame types in theconfiguration message include an UL RTS frame type, an UL CTS frametype, or both, and the one or more conditions in the configurationmessage include at least a first condition for using the UL RTS frametype, at least a second condition for using the UL CTS frame type, orboth.
 21. The apparatus of claim 20, wherein the UL RTS frame type andthe CTS frame type include at least one of: a legacy RTS frame or alegacy CTS frame, a legacy RTS frame or a legacy CTS frame wrapped incontrol wrapper frame, a legacy RTS frame or a legacy CTS frame with oneor more bits redefined to carry new information, a RTS frame or a legacyCTS frame with advanced control frame subtype, or a RTS frame or alegacy CTS frame for multi-user operation.
 22. The apparatus of claim20, wherein the CTS frame type include at least one of: a DirectionalMulti-Gigabit (DMG) CTS frame type, a DMG CTS wrapped in control wrapperframe, a DMG CTS with one or more bits redefined to carry newinformation.
 23. The apparatus of claim 19, wherein the one or moreframe types in the configuration message include a first frame type foruse as an UL CTS frame type to respond to a second frame type differentfrom the first frame type.
 24. The apparatus of claim 19, wherein theone or more frame types in the configuration message include an UL RTSframe type configured to be deferred by overlapping basic service set(OBSS) nodes.
 25. The apparatus of claim 19, wherein the one or moreconditions in the configuration message include at least one of thefollowing conditions associated with using the UL RTS frame: a receivedsignal strength indication (RSSI) is less than a RSSI threshold, amodulation and coding scheme (MCS) index value is less than a MCSthreshold, a PLCP protocol data unit (PPDU) duration is greater than aPPDU threshold, a transmit opportunity (TXOP) is greater than a TXOPthreshold, a PLCP service data unit (PSDU) size is greater than a PSDUsize threshold, a retransmission number is greater than a retrythreshold, a packet error rate (PER) is greater than a PER threshold, oran available bandwidth is greater than a bandwidth threshold.
 26. Theapparatus of claim 19, wherein the configuration information in theconfiguration message further indicates a type of information includedin each of the one or more frame types.
 27. The apparatus of claim 26,wherein the type of information included in a first frame type of theone or more frame types contains at least one or more of: informationfor spatial reuse by the STA, information for buffer status, informationfor link adaptation, information for multi-user RTS/CTS operation,information for an operation mode, information for TXOP extension, orinformation for power saving.
 28. An apparatus for wirelesscommunication, comprising: a processor; and a memory coupled to theprocessor, wherein the memory includes instructions executable by theprocessor to: receive, at a station (STA), a configuration message froman access point (AP), the configuration message including configurationinformation to configure uplink (UL) transmissions to be used by the STAas part of a request-to-send/clear-to-send (RTS/CTS) protocol, theconfiguration information indicating one or more frame types from aplurality of frame types supported by the STA for the UL transmissionsof the RTS/CTS protocol, one or more conditions for the STA to use theone or more frame types, and one or more transmission parameter valuesfor the STA to transmit with the one or more frame types; configure theSTA based on the configuration information provided in the configurationmessage; and perform, by the configured STA, the UL transmissions of theRTS/CTS protocol.
 29. The apparatus of claim 28, wherein: the one ormore frame types in the configuration message include an UL RTS frametype, an UL CTS frame type, or both, and the one or more conditions inthe configuration message include at least a first condition for usingthe UL RTS frame type, at least a second condition for using the UL CTSframe type, or both.
 30. The apparatus of claim 28, wherein the one ormore conditions in the configuration message include at least one of thefollowing conditions associated with using the UL RTS frame: a receivedsignal strength indication (RSSI) is less than a RSSI threshold, amodulation and coding scheme (MCS) index value is less than a MCSthreshold, a PLCP protocol data unit (PPDU) duration is greater than aPPDU threshold, a transmit opportunity (TXOP) is greater than a TXOPthreshold, a PLCP service data unit (PSDU) size is greater than a PSDUsize threshold, a retransmission number is greater than a retrythreshold, a packet error rate (PER) is greater than a PER threshold, oran available bandwidth is greater than a bandwidth threshold.